Reduce chatty warnings in network and replication services #467
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
warn!
(justdebug!
) when a session wasn't found for a replication message, this has normally been followed by the actual error which closed the sessionlibp2p
in the network service todebug!
(onlywarn!
when it's a connection closure event that we are explicitly responding to in panda land)warn
when dial attempts fail, this is normally because there is an existing dial attempt in progress, it's not an actual connection error, these get picked up elsewhere.📋 Checklist
Add tests that cover your changesCHANGELOG.md